Great catch

Unfortunately it won't work if values are updated, which may be the case because some options are callbacks and users might provide inlined arrow functions

I suggest using the useGetter() hook above to solve this more reliably once for all

  const getLatestOptions = useGetter(options);

  const reset = useCallback(() => setValue(getLatestOptions().initialState(getLatestOptions())), [
    setValue,
    getLatestOptions,
  ]);

(also worth applying to other methods as well, we don't follow the rules of hooks very strictly here 😅 )

Right, this still isn't stable if anon callbacks are passed, but it at least handles the case of empty options being passed (a potentially common use case).

Thanks for linking to your issue on useGetter in the code. It was fascinating to see other lib/hook authors face these changes. I don't want to pull the argument over here, but my read on the responses is that the useGetter pattern is pretty dangerous to use. In my limited experience, I've gone to great lengths to keep callbacks stable and I've documented to users what they are responsible for memoizing. It's an uphill battle and we need help from React core to make it easier, but I feel it's the safest solution in userland.

I don't feel comfortable updating to useGetter. If you'd like this PR as is, go ahead and merge it. Otherwise, I recommend closing it out or commandeering.